Define Explicit Public API Surface for Avro modules#2766
Define Explicit Public API Surface for Avro modules#2766sungwy wants to merge 2 commits intoapache:mainfrom
Conversation
|
This pull request has been marked as stale due to 30 days of inactivity. It will be closed in 1 week if no further activity occurs. If you think that's incorrect or this pull request requires a review, please simply write any comment. If closed, you can revive the PR at any time and @mention a reviewer or discuss it on the dev@iceberg.apache.org list. Thank you for your contributions. |
|
This pull request has been closed due to lack of activity. This is not a judgement on the merit of the PR in any way. It is just a way of keeping the PR queue manageable. If you think that is incorrect, or the pull request requires review, you can revive the PR at any time. |
|
@sungwy Do you need any help with this PR? |
|
This pull request has been marked as stale due to 30 days of inactivity. It will be closed in 1 week if no further activity occurs. If you think that's incorrect or this pull request requires a review, please simply write any comment. If closed, you can revive the PR at any time and @mention a reviewer or discuss it on the dev@iceberg.apache.org list. Thank you for your contributions. |
2 participants
Rationale for this change
Reduce unintentionally exposed public surface. Related issue: #1099
Are these changes tested?
Are there any user-facing changes?
Yes - and intentionally so. The number of public APIs exposed through the avro modules will be reduced significantly.
A quick search through Daft and DuckDB showed no direct usage of
pyiceberg.avromodule and its child modules in their non-test code.TODO: